*************************************************** ** NP00629 FILE ** ** DATE = 02/19/97 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA02644 = pd_sysmon.trc shows repeated restarts of GateD daemon even though it is already started. It is believed that sysmon gets ahold of a pid number that is not correct for GateD and loops on a GateD process restart when in fact GateD is already running. Local Fix: Reboot the router APARTXT NA02714 = Add option to dlstools to clear a conversation based on Data Link Correlator and do some checking before the conversation is cleared. Using this option, conversations in steady states, connected and circuit established, cannot be cleared. Also, the conversation must be 'stuck' in its current state for a period of time. This option will prevent someone from clearing the wrong conversation using the Data Link Correlator. APARTXT NA02715 = The customer Caremark is getting stuck in state 21 (Halt LS No Ack) s ince switching to rfc1795 compliant code. Following is the scenario for what is happening. A CUR_ex is received by the Analyst, who LANCASTs a TESTFRAME to all four DLSw LAN ports. (This is significant because to hit this problem you need multiple LAN ports, AND more then one of them that "can reach" the de stination MAC.) The four Lanwrites send out TEST commands and all four get TEST responses. As the TEST responses are processed by Lanread, a DLC_HALT_LS is issu ed back to the LLC because this is an explorer flow, and a RESPFRAME is sent bac k to the Analyst. The first RESPFRAME is received by the Analyst and generate s a ICR_ex back to the remote side. The following three RESPFRAMEs are received and since a match is not found in the OSCUR database for these, the Analyst gen erates a HALTLS_NOW message back to Lanwrite to clean up the link station beca use this is an extra, unneeded conversation. Well, since this is an explorer flo w, the link station has already been cleaned up. But, because some other unrelat ed link station might have been started in the mean time, using the now unused link s tation correlator that is listed in the HALTLS_NOW, when the Lanwrite gets t he HALTLS_NOW, it sends a DLC_HALT_LS for this new link station and puts it in state HALTLS_NO_ACK. The GDLC that is passed with the HALT_LS is for some other, unrelated link stations (GDLCs are unique per port, ie GDLC 1 on port 1 refers to a different LS then GDLC 1 on port 2), so when the STAH_RES comes back, the "DLSw" LS ID is diff erent that the one given on the HALT_LS. Thus, the original LS put in HALTLS_NO_ACK will remain there forever, plus another unrelated conversation is halted for no r eason. This defect only relates to RFC 1795 code, so should not be migrated to v1r3_p383fx!!!! APARTXT NA02716 = On activation, gated exits with a parsing error on the gatedtrace.ctl file. Router is up, but no gated. APARTXT NA02744 = When LANREAD receives a DLC_STAS_RES exception while in HALTLS_NO_ACK state, it sends a message with type 0 to its DLSw partner. No message should be sent when in this state. APARTXT NA02745 = Configuring an IP udp parm caused srb to become disabled. Also, configuring on any port that had both TB and SRB configured a parm that would not cause a reboot for 1 bridge type would cuase the other to be disabled. APARTXT NA02754 = With new Tama data center, some OSPF ABRs go to 100 percent utilization when many routers are brought up and down. APARTXT NA02768 = Internal Enhancements for NP00644 APARTXT NA02771 = inventory changes for r4ap level APARTXT NA02822 = ip does not work over frame realay in NP00627. If config shows interface to be broadcast instead of framerelay. APARTXT NA02832 = Internal Enhancements for NP00627 ENDSET COMPID FOR PTF NP00629 = 564801600,140 PRODID FOR PTF NP00629 = 5648016,Multiprotocol Network Program PREREQ FOR NP00629 = NONE ENDSET COREQ FOR NP00629 = NONE ENDSET SUP FOR NP00629 = NONE ENDSET IFREQ FOR NP00629 = NONE ENDSET MEMO TO USERS = +--------------------------------------------------------------+ | | | MEMO FOR NP00629 | | | | 629 01 | +--------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00629 o Engineering PTFs with contents included in Production PTFs SUPERSEDE AND PREREQUISITE PTF'S ________________________________ PTF NP00629 is a supersede PTF. The installation of a supersede PTF allows the user to apply a single PTF in order to upgrade from any PTF level in the superceded chain to the supercede PTF level. This PTF contains all the resolved APARs in the supersede Following is the superseded chain for V1R4: -base level- NP00620 NP00623 NP00625 NP00627 There are no prereq PTFs for applying NP00629 so that a user at any PTF in the supersede chain or at base level may apply the supersede PTF, NP00629. V1R4 at NP99931 (base V1R4) and PTF NP00666 or higher (V1R4 Configuration Program) is required(PTF NP00668 is recommended). +--- VERY IMPORTANT:-------------------------------------------+ | | | | | It is very important that V1R4 (NP99931) be applied | | and committed before applying PTF NP00629. | | | +--------------------------------------------------------------+ PTF INSTALL INSTRUCTIONS FOR NP00629 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ========================== FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply it. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611. Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00629. In the second selector screen you must use "none" as a selection if that is the only choice or if you you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00629) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00629 is committed all of its' prerequisites will also be commited, and any EPTF's associated with them will be rejected. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ENGINEERING PTF'S WITH CONTENTS INCLUDED IN PRODUCTION PTF'S ------------------------------------------------------------ When PTF NP00629 is committed any EPTF that was associated with PTF: NP99931 (base V1R4) NP00620 NP00623 NP00625 NP00627 will be rejected automatically. Installation of PTF NP00629 along with the prerequisite and corequisite PTF's will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX62503 FX62504 FX62701 END OF MEMO - NP00629 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************